feat(documents): add support for start ixp extraction from attachment#1239
Open
alexandrujircan wants to merge 1 commit intomainfrom
Open
feat(documents): add support for start ixp extraction from attachment#1239alexandrujircan wants to merge 1 commit intomainfrom
alexandrujircan wants to merge 1 commit intomainfrom
Conversation
github-actions
bot
added
test:uipath-langchain
There was a problem hiding this comment.
Pull request overview
Adds support for starting IXP extraction by digitizing from an existing UiPath job attachment, in addition to the existing file/file_path upload flow.
Changes:
- Extend
DocumentsService.start_ixp_extraction{_async}to accept anattachmentparameter (mutually exclusive withfile/file_path). - Add digitization helpers for the
/digitization/startFromJobAttachmentendpoint (sync + async). - Add unit tests covering the new attachment-based extraction path and update validation error expectations.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
src/uipath/platform/documents/_documents_service.py |
Adds attachment-based digitization and wires attachment into IXP extraction start APIs. |
tests/sdk/services/test_documents_service.py |
Adds UTs for the attachment-based IXP extraction path and updates invalid-parameter assertion. |
src/uipath/platform/attachments/attachments.py |
Updates the Attachment model docstring. |
Comments suppressed due to low confidence (1)
src/uipath/platform/documents/_documents_service.py:1015
- The
start_ixp_extractiondocstring says it “uploads the file as an attachment”, but the newattachmentparameter allows starting digitization from an existing job attachment without uploading. Please reword the description to reflect both code paths (upload fromfile/file_pathvs using an existingattachment).
attachment: Optional[Attachment] = None,
) -> StartExtractionResponse:
"""Start an IXP extraction process without waiting for results (non-blocking).
This method uploads the file as an attachment and starts the extraction process,
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
alexandrujircan
force-pushed
the
feat/documents/add-support-for-start-extraction-from-attachment
branch
from
b6005ea to
262013b
Compare
alexandrujircan
force-pushed
the
feat/documents/add-support-for-start-extraction-from-attachment
branch
from
262013b to
af3231b
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
vlupoaie
approved these changes
Jan 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
add support for start IXP extraction from attachment
Tested locally + added UTs